home *** CD-ROM | disk | FTP | other *** search
-
- NOVELL TECHNICAL INFORMATION DOCUMENT
-
- TITLE: FLeX/IP 1.2B Running with NetWare 4.01 & 3.x
- DOCUMENT ID: TID000563
- DOCUMENT REVISION: B
- DATE: 03DEC93
- ALERT STATUS: Yellow
- INFORMATION TYPE: Symptom Solution
- README FOR: FLX146.EXE
-
- NOVELL PRODUCT and VERSION:
- NetWare FLeX/IP 1.2
-
- ABSTRACT:
-
- This patch is neccessary for FLeX/IP 1.2B to run on both the NW 4.01 and NW
- 3.12 platforms. It also includes fixes for FTPSERV.NLM, PLPD, LPR_GWY and
- XCONSOLE.NLM. Please read this document for instructions on how to apply this
- patch.
-
- ──────────────────────────────────────────────────────────────────────────────
- DISCLAIMER
- THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
- MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
- INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
- MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
- ──────────────────────────────────────────────────────────────────────────────
-
- Self-Extracting File Name: FLX146.EXE Revision: B
-
- Files Included Size Date Time Version
-
- \
- FLX146.TXT (This File)
- LPR_IP.ISC 79204 05-04-93 3:55p
- PLPDDEF.EXE 184719 11-12-90 12:12a
- PRINTDEF.HLP 36714 05-29-90 2:41p
- BCASTLIB.NLM 904 05-06-93 10:16a
- INETDFIX.NLM 733 05-06-93 11:37a
- LPR_IP.SCO 73024 05-04-93 3:56p
- PATCH.EXE 78129 01-19-93 12:18a
- LPRINST 2515 05-04-93 3:54p
- LPSTAT.ISC 65592 05-04-93 3:56p
- LPSTAT.SCO 60076 05-04-93 3:56p
- FLX40.BAT 4924 05-27-93 10:15a
- FLX311.BAT 4623 05-27-93 10:12a
- INSTALL.BAT 507 05-27-93 10:23a
- HOWTOPA.TCH 315 05-27-93 10:29a
- PTF-F146.RTP 65724 06-17-93 2:57p
- LPR_PSRV.NLM 53696 05-06-93 11:36a
- LPR_GWY.NLM 23390 05-06-93 11:31a
- XCONSOLE.NLM 80041 05-24-93 9:55a
- PLPD.NLM 43216 05-17-93 4:14p
- RPCBSTUB.NLM 736 05-06-93 10:45a
- FILTER.NLM 18932 05-06-93 10:45a
- FLTRLIB.NLM 2315 05-06-93 10:44a
-
-
- NetWare FLeX/IP
-
- Patch for NetWare 4.01 Release Document
-
- FLX146.TXT
-
-
- Copyright (c) 1993 Novell, Inc. All Rights Reserved.
-
-
-
- THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND
- TREATIES. NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED, COPIED,
- DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED, CONDENSED,
- EXPANDED, COLLECTED, COMPILED, LINKED, RECAST, TRANSFORMED, OR ADAPTED
- WITHOUT THE PRIOR WRITTEN CONSENT OF NOVELL, INC. ANY USE OR EXPLOITATION
- OF THIS WORK WITHOUT AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO
- CRIMINAL AND CIVIL LIABILITY.
-
- **********************************************************
- CAUTION
- **********************************************************
- ALWAYS backup your system before implementing any program/utility
- revision involving the low-level functions of NetWare including
- re-linking of operating system .OBJ files, Bindery utilities, and drive
- and volume operation.
-
- This document includes the following sections:
-
- PURPOSE OF THIS PATCH
- UPDATES TO FLeX/IP
- USING XCONSOLE
- USING UNIX-TO-NETWARE PRINTING (PLPD)
- USING NETWARE-TO-UNIX PRINTING (LPR_GWY)
- LP PRINT CLIENT SOFTWARE FOR SCO OR INTERACTIVE UNIX
- USING TOKEN-RING BOARDS
- USING THIS PATCH WITH NETWARE 4.01
- CONFIGURING THE SOFTWARE TO RUN WITH NETWARE 4.01
- USING THE DIFFERENT MODES OF PCONSOLE
- CONFIGURING UNIX-TO-NETWARE PRINTING (PLPD)
- CONFIGURING NETWARE-TO-UNIX PRINTING (LPR_GWY)
- CONTROLLING JOBS
- CONFIGURING DEVICES AND FORMS USING PLPDDEF
- INSTALLING THE PATCH
-
-
- PURPOSE OF THIS PATCH
- ---------------------
-
- This patch allows the NetWare FLeX/IP product to run on a NetWare 4.01
- server and also provides updates to NetWare FLeX/IP running on a NetWare
- 3.X server. Although this patch allows the NetWare FLeX/IP product to run
- correctly on a NetWare 4.01 Server, it does not allow FLeX/IP to take
- advantage of all of the new features in NetWare 4.01, such as NetWare
- Directory Services (NDS), and enabling for National Language Support and
- double-byte character sets. After you apply this patch, the patched NLMs
- must be run in Ring 0 on NetWare 4.01 servers.
-
-
- UPDATES TO FLeX/IP
- ------------------
-
- The following sections provide updates to the existing NetWare FLeX/IP
- product running on a NetWare 3.X or NetWare 4.01 server.
-
-
- USING XCONSOLE
- --------------
-
- USING XCONSOLE WHEN A FILE SERVER IS LOCKED
- -------------------------------------------
-
- In previous versions of NetWare FLeX/IP, it was possible for an XConsole
- user to bypass a file server lock after the console screen was locked
- using the MONITOR utility. The user could unlock the screen by typing
- <Ctrl-z>, which displayed the "Select Screen" menu. From this menu the
- user could access the Console Screen and unload monitor NLM. This patch
- fixes this problem by disabling <Ctrl-z> when a file server lock is set
- from the MONITOR utility.
-
- USING XCONSOLE WITH HOST PRESENTER
- ----------------------------------
-
- When an XConsole session is terminated from Host Presenter "File Menu"
- without pressing <Ctrl-X>, or from TNVT220 by switching back to the
- terminal <Alt-t> and then exiting the session (q), the following error
- message appears in the audit log:
-
- Xconsole-Error: :Telnetd failed writing to client,
- reason - an asynchronous event has occurred
-
- You should ignore this error message.
-
- KEY MAPPING IN XCONSOLE
- -----------------------
-
- If your terminal does not have the <Backspace> key or you prefer to use
- the <Delete> key (on the main keypad) for the "Erase Previous Character"
- operation, then you can use <Ctrl-h> or re-map your delete key to send
- the code XK_Backspace.
-
- USING AN ICON DURING AN XCONSOLE SESSION
- ----------------------------------------
-
- When you XConsole iconize an XConsole session, the icon name is the
- NetWare server name instead of "NetWare".
-
- USING A 24 LINE TERMINAL WITH XCONSOLE
- --------------------------------------
-
- If you load XConsole with the /24 switch as follows:
-
- :load xconsole /24
-
- Lines 2 through 25 of the NetWare Server's Console will be displayed.
- The first line will not be displayed.
-
-
- USING UNIX-TO-NETWARE PRINTING (PLPD)
- -------------------------------------
-
- PRINTING A BANNER PAGE
- ----------------------
-
- In previous versions of NetWare FLeX/IP, you could not print a banner if
- you selected the "None" filter option from within the UNIX-to-NetWare
- Print menu of the FLEXCON utility or from within the PLPDCFG utility. A
- banner will now be printed in this case, unless you disable the banner
- using the "-J/nb" option of the LPR command.
-
- Most LP print clients send their print requests with banner page and
- trailing form feed enabled by default.
-
- If the LP print client sends a special title switch "/nff/nb" to PLPD in
- the -J option of lpr, PLPD overrides the client's request and suppresses
- both trailing formfeed and the banner page for that particular print job.
-
- For example:
-
- lpr -Pnetware -J/nff/nb <filename>
-
- For banner page suppression only, you should use the lpr -h switch or the
- lpr -J/nb switch.
-
- For trailing formfeed suppression only, you should use the lpr -J/nff
- switch.
-
- PLPD ERROR MESSAGES
- -------------------
-
- When printing under busy conditions, you might see the following error
- message on the PKERNEL message screen at NetWare v3.1x servers (the
- message does not appear on NetWare 4.01 servers:
-
- PLPD-Error: Cannot create temporary spool file
-
- If printing appears to be normal, ignore this error message. If a job
- appears to take a long time to print, you should update the CLIB.NLM to
- version 3.11d or greater. New version of CLIB.NLM is available from
- NetWire NOVLIB Forum.
-
-
- USING NETWARE-TO-UNIX PRINTING (LPR_GWY)
- ----------------------------------------
-
- In previous versions of NetWare FLeX/IP, the server would crash when the
- print gateway tried to connect to a remote host where the printer was
- off-line or not available. This no longer happens.
-
- In previous versions of NetWare FLeX/IP, the LPR_GWY did not handle the
- "T" and "H" flags of the control file properly. The LPR_GWY will now
- handle these flags and send the proper print control information to the
- UNIX lpr print server.
-
-
- LP PRINT CLIENT SOFTWARE FOR SCO OR INTERACTIVE UNIX
- ----------------------------------------------------
-
- This patch updates the files that allow printing from SCO and Interactive
- Unix v3.2 print clients.
-
- Now that SCO and Interactive have their own lp implementation, you should
- use the lpr support from SCO or ISC whenever possible.
-
-
- USING TOKEN-RING BOARDS
- -----------------------
-
- When using Token-Ring boards, the maximum size of receive buffers must be
- set to 4202. To setup this server configuration when the server is
- restarted, add the following line to the STARTUP.NCF file:
-
- set maximum physical receive packet size=4202
-
-
- USING THIS PATCH WITH NETWARE 4.01
- ----------------------------------
-
- The following sections describe important information that you should
- know before using FLeX/IP on a NetWare 4.01 server.
-
-
- CONFIGURING THE SOFTWARE TO RUN WITH NETWARE 4.01
- -------------------------------------------------
-
- Bindery emulation is an essential part of running NetWare FLeX/IP on a
- NetWare 4.01 server. Before you use this patch, you must plan and then
- set up bindery emulation on your NetWare 4.01 server. Novell recommends
- that you use the NetWare 4.01 documentation and the June 1993 edition of
- NetWare Application Notes entitled "NetWare 4.0 Bindery Emulation: An
- Overview" to set up bindery emulation.
-
- The Bindery Context must be set on this server for this patch to work
- correctly.
-
- You must set the Bindery Context to the position in the directory tree
- where the server's volumes are located. For example, if the server
- volumes are located in
-
- OU=Department.O=Company
-
- you would have the following line in your AUTOEXEC.NCF file
-
- SET BINDERY CONTEXT = OU=Department.O=Company
-
- To view the server's current bindery emulation context, type
-
- SET BINDERY CONTEXT <Enter>
-
- This command displays the server's current bindery emulation context.
-
-
- USING THE GROUP EVERYONE
- ------------------------
-
- In NetWare 4.01, the group EVERYONE is not automatically created and
- updated as it is in NetWare 3.X. For example, if you create a user object
- before you create the group EVERYONE, the user object does not get added
- when you create the group EVERYONE in NetWare 4.01. If you upgraded from
- a NetWare 3.X server, then the group EVERYONE was updated during
- installation. If you installed NetWare 4.01 on a clean server, and the
- group EVERYONE does not exist, you should create the group and add users
- to it.
-
- When using NetWare 4.01, you must remember that using the group EVERYONE
- does not automatically mean that all users will have access to a service.
- Whenever you add a new queue, print server, or any object where the group
- EVERYONE is granted rights to use the service, you must check that all
- users are members of the group EVERYONE. For example, if you use the PLPD
- and LPR_GWY NLMs, and you give the group EVERYONE access to these
- services, it is your responsibility to make sure that all users are
- included in the group EVERYONE. In this case, any user trying to print
- that is not in the group EVERYONE will be denied queue access.
-
-
- USING THE DIFFERENT MODES OF PCONSOLE
- -------------------------------------
-
- The new PCONSOLE utility has two modes of operation. When you run
- PCONSOLE on a NetWare 4.01 server, it starts in Directory Services mode.
- If you press the <F4> key from within PCONSOLE, it enters Bindery mode.
- When you are in Bindery mode, you can view queues, printers, and print
- servers created using the FLEXCON utility because the FLEXCON utility
- creates only bindery objects.
-
- Some bindery objects can also be accessed from the Directory Services
- mode, but remember that Directory Services replaces all underscores in
- bindery names with spaces. For example, if you create a print server
- named "ps_for_lab" using the FLEXCON utility, its name would appear as
- "ps for lab" from the Directory Services mode of PCONSOLE.
-
- The <F4> key allows you to switch between the two modes of operation
- (Bindery mode and Directory Services mode). Before you use the Bindery
- mode you must be logged into the current server as a user in the Bindery
- Context.
-
- IMPORTANT: ADMIN can only use Bindery mode if ADMIN is in the current
- Bindery context.
-
-
- CONFIGURING UNIX TO NETWARE PRINTING (PLPD)
- -------------------------------------------
-
- You may use the NetWare 4.01 PCONSOLE utility and the FLEXCON utility to
- configure UNIX-to-NetWare printing. You use PCONSOLE to create and
- associate queues, printers, and print servers and the PLPDCFG to select
- queues for use by UNIX printing, trusted hosts, and user account mapping.
- The following sections describe the configuration procedure.
-
- IMPORTANT: You also have the ability to create queues using the
- FLEXCON and PLPDCFG utilities, but Novell strongly
- suggests that you do not create queues using this method.
- If you create a queue using either the FLEXCON or PLPDCFG
- utilities, the queue will provide UNIX-to-NetWare
- printing, but your ability to control and view jobs
- through PCONSOLE will be limited.
-
- CONFIGURING USING PCONSOLE
- --------------------------
-
- The following configuration can be done from either mode of PCONSOLE.
-
- 1. From a NetWare 4.01 client, log into the NetWare 4.01 Directory
- and run the PCONSOLE utility.
-
- 2. Create queues, printers, and print servers from within PCONSOLE.
-
- Remember that you need to associate each queue with a printer, and then
- specify which printers are serviced by each print queue.
-
- The NetWare 4.01 Print Services Manual describes how to use the new
- PCONSOLE utility in detail.
-
- >From within the "Queue Information" and "Print Server Information"
- menus, the administrator also needs to specify users for the queues and
- print servers used by PLPD. If you use the group named EVERYONE, it is
- important that you check to make sure that all users are included in the
- group EVERYONE (see the section titled "Using the Group Everyone" at the
- beginning of this document.)
-
- IMPORTANT: The print queues that you create for use by the FLeX/IP
- product must reside on a volume that physically resides on
- the server where the FLeX/IP product is running.
-
- CONFIGURING USING THE UNIX-TO-NETWARE MENU OF FLEXCON
- -----------------------------------------------------
-
- The configuration procedure for UNIX-to-NetWare printing using the
- FLEXCON utility has not changed for this patch. When mapping users, it is
- important to know that the user named GUEST might not exist in NetWare
- 4.01. If you upgraded your server from a NetWare 3.X server to a NetWare
- 4.01 server, the user named GUEST was created, but if you installed on a
- clean server, the user named GUEST does not exist.
-
- If you cannot find the user named GUEST, you can create the user named
- GUEST from the NETADMIN utility, or you can map UNIX users to a different
- NetWare account.
-
-
- CONFIGURING NETWARE-TO-UNIX PRINTING (LPR_GWY)
- ----------------------------------------------
-
- You configure NetWare-to-UNIX printing using the FLEXCON utility. The
- configuration procedure for using the FLEXCON utility has not changed for
- this patch.
-
- The following sections describe the relationship between PCONSOLE objects
- (queues, printers, and print servers) and the FLEXCON utility.
-
- PRINTERS
- --------
-
- Printers created using the FLEXCON utility are only visible from the
- Bindery mode of PCONSOLE.
-
- QUEUES & PRINT SERVERS
- ----------------------
-
- Queues and Print Servers are visible from both modes in PCONSOLE.
-
- OBJECT NAMES
- ------------
-
- PCONSOLE replaces all underscores in object names with spaces. For
- example, if you create a print server named "ps_for_lab" using the
- FLEXCON utility, its name appears as "ps for lab" in the Directory
- Services mode of PCONSOLE.
-
- IMPORTANT: When you create queues using the FLEXCON utility, the
- group named EVERYONE is assigned as the only queue user.
- It is important to check that the group named EVERYONE
- includes all users that need to print from NetWare-to-UNIX
- using the this queue. PCONSOLE can be used to add users to
- the group EVERYONE, or to restrict access to the queue.
- New queue users can be assigned from within PCONSOLE.
-
-
- CONTROLLING JOBS
- ----------------
-
- You can use the PCONSOLE utility to control jobs for both PLPD and
- LPR_GWY.
-
- UNIX TO NETWARE PRINTING:
- -------------------------
-
- You can remove pending jobs from queues and control printers by using the
- Directory Services mode of PCONSOLE.
-
- NETWARE-TO-UNIX PRINTING:
- -------------------------
-
- You can remove queued jobs from a specific queue using the Directory
- Services mode of PCONSOLE.
-
- If you want to control printers created by the FLEXCON utility, you must
- enter the Bindery mode of PCONSOLE by pressing the <F4> key. (Printers
- created using the FLEXCON utility display only under Bindery mode.)
-
- You must be a Print Server operator to enter Bindery mode and change the
- status of the printer. If you need to create a print server operator
- within the bindery context, log in as ADMIN and create an operator using
- the Directory services mode of PCONSOLE. After you add the new operator,
- you must unload and then reload the LPR_GWY and LPR_SRV so that the
- changes take effect.
-
-
- CONFIGURING DEVICES AND FORMS FOR PLPD USING PLPDDEF
- ----------------------------------------------------
-
- PLPD does not work with the new PRINTDEF utility supplied with NetWare
- 4.01. A new DOS client utility named PLPDDEF is supplied with this patch
- to allow users to configure print devices and forms for PLPD. This new
- utility has the same user interface as the PRINTDEF utility distributed
- with NetWare 3.X.
-
- The PLPDDEF utility allows PLPD users to configure forms and print
- devices (printers and plotters), which are used by PLPD. In most cases,
- the PLPDDEF utility operates similarly to the NetWare 4.01 PRINTDEF
- utility. There are two main differences between the two utilities. The
- first is that the PRINTDEF utility requires a context setting because it
- stores information in the NetWare 4.01 Directory, while the PLPDDEF
- utility does not have a context. The second difference is that the
- PLPDDEF utility stores information in SYS:PUBLIC/NET$PRN.DAT. This
- database cannot be shared by the PRINTDEF utility in NetWare 4.01 or by
- multiple servers.
-
- In general, the documentation on the PRINTDEF utility supplied with
- NetWare 3.X or NetWare 4.01 can be used with the PLPDDEF utility except
- for any NetWare 4.01 references to setting a Context.
-
- USING PLPDDEF:
- --------------
-
- After logging into the NFS Server, change directories to SYS:PUBLIC of
- the server where the FLeX/IP NLMs are loaded and run the PLPDDEF program.
-
- Warning: You must be logged into the server as a user located within the
- Bindery Context. If you are logged in as user1 and your Bindery Context
- is set to OU=department.O=company, then user1 must be located within the
- directory OU=department.O=company.
-
-
- INSTALLING THE PATCH
- --------------------
-
- This patch updates the NetWare FLeX/IP product on NetWare 3.X servers and
- incorporates extended features to run on NetWare 4.01 by patching the
- files listed below. After the patch is applied to the files, they will
- match the version number shown in the second column.
-
- MODULE VERSION
-
- PLPD.NLM 1.27b
- PKERNEL.NLM 2.20b
- XCONSOLE.NLM 1.27b
- NFS.NAM 1.27b
- V_NFS.NLM 1.20b
- RPCBSTUB.NLM 1.20b
- FILTER.NLM 1.20b
- FLTRLIB.NLM 1.20b
- PLPDCFG.NLM 1.20b
- LPR_PSRV.NLM 1.20b
- LPR_GWY.NLM 1.20b
- FTPSERV.NLM 1.20b
- INETD.NLM 1.20b
- FLEXCON.NLM 1.27b
- BCASTLIB.NLM (3.X only) 1.20b
- INETDFIX.NLM (3.X only) 1.20b
- PLPDDEF.EXE (4.01 only) Not Applicable
- PRINTDEF.HLP (4.01 only) Not Applicable
-
- FILES FOR THIS PATCH
- --------------------
-
- PLPDDEF.EXE
- PRINTDEF.HLP
- FLX146.TXT
- PTF-F146.RTP
- PATCH.EXE
- BCASTLIB.NLM
- INETDFIX.NLM
- FLX311.BAT
- FLX40.BAT
-
- PREPARING TO INSTALL
- --------------------
-
- Before you start the PATCH procedure, make sure you have the following:
-
- >> NetWare FLeX/IP installed on your server.
- >> Workstation with a floppy disk drive with the same format as the
- distribution diskette and 1MB of disk space.
- >> Patch files on hard disk..
- >> You must have 2 Mb of disk space to apply this patch.
-
- Before you begin this procedure, you must login to the server as ADMIN or
- SUPERVISOR from a DOS workstation.
-
- This patch installation procedure makes the following assumptions:
-
- Drive C: is assumed for all activities on the local hard drive.
- Drive F: is assumed for all activities related to the NetWare server.
-
- Make sure that you substitute the correct drive letters for the ones
- listed above if your configuration is different.
-
- You need to create a temporary directory for this procedure named TEMP1.
- If this name is already used on this workstation, use another name for
- the temporary directory where TEMP1 is specified in this procedure.
-
- PATCHING THE NLMS FROM A DOS WORKSTATION
- ------------------------------------------
-
- 1.Create a temporary directory on the workstation. This directory
- will contain the PATCH files and the NLMs. (This procedure assumes
- the temporary directory is created on drive C:. Substitute the
- actual drive letter to be used for C:.)
-
- C:> MKDIR \TEMP1 <Enter>
-
- 2.Change to the temporary directory.
-
- C:
- CD \TEMP1 <Enter>
-
- 3.Copy the patch files to the temporary directory. The following
- instruction assumes that you are copying the patch files from a
- diskette in the A: drive.
-
- COPY A:*.*
-
- 4.Map drive F: to SYS:
-
- MAP F:=SYS: <Enter>
-
- 5.Make sure that a search dive is mapped to the SYS:PUBLIC
- directory.
-
- 6.Perform one of the following instructions:
-
- If you are running NetWare v3.X, type:
-
- FLX311 F: <Enter>
-
- If you are running NetWare v4.01, type:
-
- FLX40 F: <Enter>
-
- 7.Down the server.
-
- 8.If you are running NetWare 3.X, copy the file named _NFS.NLM to
- the server's boot directory.
-
- If you are running NetWare 4.01, copy the files named NFS.NAM and
- V_NFS.NLM to the server's boot directory.
-
- 9.Reboot the server.
-
- The FLeX/IP product is now updated to include the patch.
-
-